Remote management agent apparatus, remote management system, and remote management method

ABSTRACT

A remote management agent apparatus for a remote management system is provided. The remote management system includes a remote device management apparatus and a management target device managed by the remote device management apparatus remotely. The remote management agent apparatus includes a request data receiver configured to receive request data issued from the remote device management apparatus to the management target device, a device agent apparatus identifying unit configured to identify a device agent apparatus capable of communicating in compliance with a communication mode supported by the management target device, and a request data forwarder configured to forward the request data, received by the request data receiver, to the device agent apparatus identified by the device agent apparatus identifying unit.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority under 35 U.S.C. § 119 toJapanese Patent Application No. 2017-054876, filed on Mar. 21, 2017, thecontents of which are incorporated herein by reference in theirentirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present disclosure relates to a remote management agent apparatus, aremote management system, and a remote management method.

2. Description of the Related Art

There is known a remote management system managing a number ofelectronic devices connected to a network from a remote location. In thetechnical field of the remote management system, also is known atechnique for managing electronic devices provided inside a firewallfrom a remote location outside the firewall, by installing an agentdevice inside the firewall.

For example, in a remote management method of an imaging devicedisclosed in Japanese Unexamined Patent Application Publication No.2009-32277, an agent device is installed in a local area network inwhich a firewall is provided. A management command issued from themanagement device to the agent device is transmitted via the firewall.In response to the management command, the agent device obtains statusdata from the imaging device and sends back to the management device viathe Internet. According to the technique, it is possible to manage animaging device in a local area network in which a firewall is providedfrom a management device in a remote location.

SUMMARY OF THE INVENTION

According to one aspect of the present disclosure, a remote managementagent apparatus for a remote management system is provided. The remotemanagement system includes a remote device management apparatus and amanagement target device managed by the remote device managementapparatus remotely. The remote management agent apparatus includes arequest data receiver configured to receive request data issued from theremote device management apparatus to the management target device, adevice agent apparatus identifying unit configured to identify a deviceagent apparatus capable of communicating in compliance with acommunication mode supported by the management target device, and arequest data forwarder configured to forward the request data, receivedby the request data receiver, to the device agent apparatus identifiedby the device agent apparatus identifying unit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a view illustrating an overall configuration of a remotemanagement system according to a first embodiment of the presentdisclosure;

FIG. 2 is a view illustrating a hardware configuration of each apparatusin the remote management system according to the first embodiment of thepresent disclosure;

FIG. 3 is a view illustrating a functional configuration of eachapparatus in the remote management system according to the firstembodiment of the present disclosure;

FIG. 4 is a sequence diagram illustrating a flow of a remote managementprocess performed in the remote management system according to the firstembodiment of the present disclosure;

FIG. 5 is a sequence diagram illustrating a flow of a device agentapparatus setting process performed in the remote management systemaccording to the first embodiment of the present disclosure;

FIG. 6 is a sequence diagram illustrating a flow of a management targetdevice adding process performed in the remote management systemaccording to the first embodiment of the present disclosure;

FIG. 7 is a diagram illustrating an example of first mapping informationstored in a mapping information storage unit of the remote managementsystem according to the first embodiment of the present disclosure;

FIG. 8 is a diagram illustrating an example of second mappinginformation stored in the mapping information storage unit of the remotemanagement system according to the first embodiment of the presentdisclosure;

FIG. 9 is a diagram illustrating an exemplary data structure ofcommunication mode definition information stored in a communication modedefinition information storage unit of the remote management systemaccording to the first embodiment of the present disclosure;

FIG. 10 is a diagram illustrating an exemplary data structure ofmanagement target device information stored in a management targetdevice information storage unit of the remote management systemaccording to the first embodiment of the present disclosure;

FIG. 11 is a sequence diagram illustrating a flow of a scheduleexecution process performed in the remote management system according tothe first embodiment of the present disclosure; and

FIG. 12 is a view illustrating an overall configuration of an industrialequipment management system according to a second embodiment of thepresent disclosure.

DESCRIPTION OF THE EMBODIMENTS First Embodiment

In the following, a first embodiment of the present disclosure will bedescribed with reference to the drawings.

<Overall Configuration of Remote Management System>

FIG. 1 is a view illustrating an overall configuration of a remotemanagement system 10 according to the first embodiment of the presentdisclosure. The remote management system 10 illustrated in FIG. 1 isconfigured such that multiple management target devices 14 provided inmultiple installation environments A to C can be managed via theInternet 15 and a firewall 16 from a remote device management apparatus11 that is located remotely.

As illustrated in FIG. 1, the remote management system 10 includesmultiple remote device management apparatuses 11, a remote managementagent apparatus 12, multiple device agent apparatuses 13, and multiplemanagement target devices 14. Note that a management target device withagent 14′ illustrated in FIG. 1 is a type of the management targetdevice 14 configured by adding a function similar to the device agentapparatus 13 to the management target device 14.

The remote device management apparatus 11 is operated by a remote deviceadministrator, and can monitor or operate the management target device14 from a remote location. The remote device management apparatus 11maintains device information and service definition information. Thedevice information includes information concerning a management targetdevice 14 to be managed by the remote device management apparatus 11.The service definition information includes information concerning aservice provided by the remote device management apparatus 11.

The service definition information includes, for example, eventinformation concerning an event such as a periodical health check eventor a periodical information collection event, frequency information ofan event, and definition of information which should be retrieved fromthe management target device 14. The service definition information alsoincludes communication mode definition information which is used by adevice agent apparatus 13 to communicate with a management target device14.

Examples of the services provided by the remote device managementapparatus 11 include a display of a device status used for remotemaintenance, a display of an error state, an update of setting values ofa device, a report of device usage, an acquisition of log information ofa device for a developer of the device, a remote firmware update of adevice, and an office management for managing air conditioning orlighting in an office. The remote device management apparatus 11 mayprovide a service coordinated with other Web services.

The remote management agent apparatus 12 mediates communication databetween a remote device management apparatus 11 and a device agentapparatus 13. For example, when the remote management agent apparatus 12receives request data targeted to a management target device 14 which isissued from a remote device management apparatus 11, the remotemanagement agent apparatus 12 can forward the request data to a deviceagent apparatus 13 communicably coupled to the management target device14. Also, when the remote management agent apparatus 12 receivesresponse data output from the management target device 14 via the deviceagent apparatus 13, the remote management agent apparatus 12 can forwardthe response data to the remote device management apparatus 11.

In the present embodiment, HTTP (Hypertext Transfer protocol) is usedfor communication between the remote management agent apparatus 12 andthe remote device management apparatus 11, and communication between theremote management agent apparatus 12 and the device agent apparatus 13.However, a communication protocol used for these communications is notlimited to HTTP. Other communication protocols that can be used forthese communications (such as WebSocket or MQTT) may be used.

A device agent apparatus 13, and a management target device 14 coupledto the device agent apparatus 13, are installed in the same local areanetwork. In response to receiving request data transmitted via theInternet 15 and the firewall 16 from the remote management agentapparatus 12, the device agent apparatus 13 communicates with themanagement target device 14 in compliance with a communication modesupported by the management target device 14.

By performing communication, the device agent apparatus 13 transmitsvarious request data (for example, an operation instruction such aschanging a setting value, updating firmware, and tuning on/off power, oran acquisition request of information of a management target device 14,such as status information, setting value information, and loginformation) from a remote device management apparatus 11 to themanagement target device 14, and obtains various response data from themanagement target device 14.

For example, the device agent apparatus 13 establishes connection withthe remote management agent apparatus 12 using a communication protocolsuch as HTTP, WebSocket or HTTP2. Note that the device agent apparatus13 may not necessarily be embodied by a dedicated hardware. The deviceagent apparatus 13 may be embodied by software installed in otherapparatuses (such as a server, a box appliance, or a management targetdevice 14).

A communication path between the device agent apparatus 13 and theremote management agent apparatus 12 is not limited to a path via theInternet 15. Public wireless networks such as 3G or LTE may also be usedin the communication path. In this case, the device agent apparatus 13may connect to the remote management agent apparatus 12 via VPN from anaccess point of a communication carrier.

Further, when a new management target device 14 is added, informationconcerning a communication mode supported by the new management targetdevice 14 (communication mode definition information) and communicationsetting information of the new management target device 14 (managementtarget device information) are set/registered dynamically with thedevice agent apparatus 13. By referring to the communication modedefinition information and the management target device information, thedevice agent apparatus 13 can communicate with the new management targetdevice 14.

The management target device 14 is an electronic device equipped with acommunication function, and is a target of management by a remote devicemanagement apparatus 11. Examples of the management target device 14include an imaging device (such as a printer, a fax, a digitalmultifunction peripheral, or a scanner), a network-connected homeappliance, office equipment (such as a projector or an electronicwhiteboard), a vending machine, medical equipment, power supplyequipment, air conditioning equipment, and metering equipment for gas,water, electricity, or the like. Each management target device 14 isequipped with a communication function using a specific communicationprotocol such as HTTP, SNMP, ICMP, MQTT, and the like. The communicationprotocol supported by each management target device 14 differs dependingon a type of the management target device 14.

<Hardware Configuration of Each Apparatus in Remote Management System10>

FIG. 2 is a view illustrating a hardware configuration of each apparatusin the remote management system 10 according to the first embodiment ofthe present disclosure. As illustrated in FIG. 2, each of the remotedevice management apparatus 11, the remote management agent apparatus12, the device agent apparatus 13, and the management target device 14includes a CPU (Central Processing Unit) 201, a ROM (Read Only Memory)202, a RAM (Random Access Memory) 203, a storage unit 204, an input unit205, a display unit 206, and a communication unit 207. These hardwareelements are connected with each other via a bus.

The CPU 201 executes various programs stored in the ROM 202 or thestorage unit 204. The ROM 202 is a non-volatile memory. The ROM 202stores, for example, various programs to be executed by the CPU 201 anddata necessary for the CPU 201 executing the various programs. The RAM203 is a main memory device such as DRAM (Dynamic Random Access Memory)or SRAM (Static Random Access Memory). The RAM 203 is used, for example,as a work area when the CPU 201 executes various programs.

The storage unit 204 is a non-volatile storage device. The storage unit204 stores, for example, various programs to be executed by the CPU 201and data necessary for the CPU 201 executing the various programs. Theinput unit 205 is an interface used by an operator (a deviceadministrator or the like) when inputting various instructions. Thedisplay unit 206 is a display device for displaying various information(such as various remote management screens rendered by the remote devicemanagement apparatus 11). The communication unit 207 is an interfaceused for communicating with other devices via a network.

The remote management agent apparatus 12, the device agent apparatus 13,and the management target device 14 are not required to include an inputunit 205 and a display unit 206. However, the remote management agentapparatus 12, the device agent apparatus 13, and the management targetdevice 14 may include an input unit 205 and a display unit 206, so thatan operator can input various instructions depending on functions ofeach device.

<Functional Configuration of Each Apparatus in Remote Management System10>

FIG. 3 is a view illustrating a functional configuration of eachapparatus in the remote management system 10 according to the firstembodiment of the present disclosure.

<Function of Remote Device Management Apparatus 11>

As illustrated in FIG. 3, the remote device management apparatus 11includes a communication mode definition information storage unit 310, arequest data transmitter 311, a response data receiver 312, and a remotedevice management controller 313.

The communication mode definition information storage unit 310 storescommunication mode definition information, in which a definition of acommunication mode (such as a communication protocol and a communicationport) used for a communication between a device agent apparatus 13 and amanagement target device 14 is described. Details of the communicationmode definition information will be described below with reference toFIG. 9.

The request data transmitter 311 transmits request data targeted to amanagement target device 14 to the remote management agent apparatus 12.The response data receiver 312 receives response data which is sent outfrom a management target device 14 and is forwarded by the remotemanagement agent apparatus 12.

The remote device management controller 313 controls overall remotemanagement performed by the remote device management apparatus 11. Whenan operator inputs, to the remote device management apparatus 11, aninstruction targeted to a certain management target device 14, theremote device management controller 313 causes the request datatransmitter 311 to transmit request data to the management target device14. In addition, when the response data receiver 312 receives responsedata from a management target device 14, the remote device managementcontroller 313 performs, based on the response data, a processcorresponding to the response data (for example, an error detectionprocessing, a device controlling process in case of an error, and thelike).

The remote device management controller 313 further performs informationacquisition from a management target device 14, based on servicedefinition information that is set to the remote device managementapparatus 11 in advance. The service definition information includes,for example, identification information of a management target device 14from which information is to be acquired, a type of information to beacquired, and an information acquisition frequency. The remote devicemanagement controller 313 can also generate and display various lists ofinformation concerning management target devices 14 managed by theremote device management apparatus 11. Examples of the lists include: alist of the management target devices 14 in which an error occurred, alist of the management target devices 14 used by a certain customer, andthe like.

<Function of Remote Management Agent Apparatus 12>

As illustrated in FIG. 3, the remote management agent apparatus 12includes a mapping information storage unit 320, a request data receiver321, a device agent apparatus identifying unit 322, a request dataforwarder 323, a response data receiver 324, a response data forwarder325, and a mapping information registration unit 326.

The mapping information storage unit 320 stores mapping information(also referred to as “first mapping information”) representing a mappingbetween a management target device 14 and a device agent apparatus 13 (adevice agent apparatus 13 capable of communicating in compliance with acommunication mode supported by the management target device 14). Aspecific example of the first mapping information will be describedbelow with reference to FIG. 7. The mapping information storage unit 320also stores mapping information (second mapping information)representing a mapping between a remote device management apparatus 11and a device agent apparatus 13. A specific example of the secondmapping information will be described below with reference to FIG. 8.

The request data receiver 321 receives request data which is targeted toa management target device 14, from a remote device management apparatus11.

The device agent apparatus identifying unit 322 identifies a deviceagent apparatus 13 capable of communicating in compliance with acommunication mode supported by a management target device 14.Specifically, the device agent apparatus identifying unit 322 refers tothe first mapping information stored in the mapping information storageunit 320, and identifies, out of the first mapping information, a deviceagent apparatus 13 associated with a management target device 14 whichis a destination of request data, as the device agent apparatus 13capable of communicating in compliance with a communication modesupported by the management target device 14.

The request data forwarder 323 forwards request data received by therequest data receiver 321 to a device agent apparatus 13 identified bythe device agent apparatus identifying unit 322.

The response data receiver 324 receives response data sent from amanagement target device 14 via a device agent apparatus 13.

The response data forwarder 325 sends response data received by theresponse data receiver 324 to a remote device management apparatus 11.In sending the response data, the response data forwarder 325 refers tothe second mapping information stored in the mapping information storageunit 320 to identify a remote device management apparatus 11 associatedwith the device agent apparatus 13 via which the response data is sent,and determines the identified remote device management apparatus 11 as adestination of the response data.

When a new management target device 14 is added, the mapping informationregistration unit 326 adds, to the first mapping information stored inthe mapping information storage unit 320, information representing amapping between the new management target device 14 and the device agentapparatus 13 capable of communicating with the new management targetdevice 14.

<Function of Device Agent Apparatus 13>

As illustrated in FIG. 3, the device agent apparatus 13 includes amanagement target device information storage unit 330, a communicationunit to remote management agent apparatus 331, a communication modeidentifying unit 332, a communication unit to management target device333, a management target device information registration unit 334, acommunication mode definition information setting unit 335, a scheduleinformation registration unit 336, and a schedule information storageunit 337.

The management target device information storage unit 330 storesmanagement target device information including communication settinginformation for a management target device 14 managed by the deviceagent apparatus 13. Details of the management target device informationwill be described below with reference to FIG. 10.

The communication unit to remote management agent apparatus 331 performscommunication with the remote management agent apparatus 12. Thecommunication unit to remote management agent apparatus 331 receivesrequest data sent from the remote management agent apparatus 12, andtransmits response data, received from a management target device 14 bythe communication unit to management target device 333, to the remotemanagement agent apparatus 12. In the present embodiment, HTTP is usedfor communication with the remote management agent apparatus 12, by thecommunication unit to remote management agent apparatus 331. However,other communication protocols such as WebSocket or HTTP2 may be used,instead of (or in addition to) HTTP.

The communication mode identifying unit 332 identifies a communicationmode and a communication setting used for communication with amanagement target device 14. Specifically, the communication modeidentifying unit 332 identifies the communication mode and thecommunication setting used for the communication with a managementtarget device 14, based on the communication mode definition informationset to the device agent apparatus 13 by the communication modedefinition information setting unit 335, and based on the managementtarget device information registered with the management target deviceinformation storage unit 330 by the management target device informationregistration unit 334.

The communication unit to management target device 333 performscommunication with a management target device 14 using the communicationmode and the communication setting identified by the communication modeidentifying unit 332. Based on the communication mode and thecommunication setting identified by the communication mode identifyingunit 332, the communication unit to management target device 333 sendsrequest data received by the communication unit to remote managementagent apparatus 331, to the management target device 14. Further, thecommunication unit to management target device 333 receives responsedata output by the management target device 14.

When a new management target device 14 is added, the management targetdevice information registration unit 334 adds the management targetdevice information concerning the new management target device 14 to themanagement target device information storage unit 330, in response to arequest from a remote device management apparatus 11.

When a new management target device 14 is added, the communication modedefinition information setting unit 335 sets the communication modedefinition information concerning the new management target device 14 tothe device agent apparatus 13, in response to a request from a remotedevice management apparatus 11.

The schedule information registration unit 336 registers scheduleexecution information with the schedule information storage unit 337.The schedule information storage unit 337 stores the schedule executioninformation registered by the schedule information registration unit336. Specifically, when the device agent apparatus 13 receives aregistration request of schedule execution information from a remotedevice management apparatus 11, the schedule information registrationunit 336 in the device agent apparatus 13 registers the scheduleexecution information with the schedule information storage unit 337.

For example, the following information is recorded in the scheduleexecution information:

Schedule execution: Effective/Ineffective

Schedule definition: Information collection, health check, and the like.

Schedule execution timing: Once a day/once a week/once amonth/periodical

Schedule execution time (This is set when the schedule execution timingis once a day, once a week, or once a month)

Schedule execution frequency (This is set when the schedule executiontiming is periodical)

Suppose a case in which the “Schedule execution” is set to “Effective”.In this case, when a time to perform schedule execution arrives,specified with a set of “Schedule execution timing” and “Scheduleexecution time” (or a set of “Schedule execution timing” and “Scheduleexecution frequency”), the communication mode identifying unit 332 firstidentifies a communication mode and a communication setting used forcommunication with a management target device 14. Subsequently, thecommunication unit to management target device 333 performscommunication with the management target device 14 using thecommunication mode and the communication setting identified by thecommunication mode identifying unit 332. Based on the communication, thecommunication unit to management target device 333 performs a processdefined in the “Schedule definition” (such as information collection orhealth check) to the management target device 14. When the communicationunit to management target device 333 receives a processing result fromthe management target device 14, the communication unit to managementtarget device 333 sends the processing result to a remote devicemanagement apparatus 11 via the remote management agent apparatus 12.

The device agent apparatus 13 executes the above series of processes foreach time specified with a set of “Schedule execution timing” and“Schedule execution time” (or a set of “Schedule execution timing” and“Schedule execution frequency”). Therefore, after the schedule executioninformation is registered with the device agent apparatus 13, the remotedevice management apparatus 11 can obtain information concerning themanagement target device 14 periodically.

<Function of Management Target Device 14>

As illustrated in FIG. 3, the management target device 14 includes arequest receiver 341, a processing unit 342, and a response output unit343.

The request receiver 341 receives a request from a remote devicemanagement apparatus 11 by receiving request data from a device agentapparatus 13.

The processing unit 342 performs various processes in response to arequest from a remote device management apparatus 11 received by therequest receiver 341. The processing unit 342 performs, for example, aprocess for operating the management target device 14 (where theprocessing unit 342 resides), such as changing a setting value, updatingfirmware, or turning on/off power. The processing unit 342 alsoperforms, for example, a process for outputting various types ofinformation (such as a state, a setting value, or log information of themanagement target device 14).

The response output unit 343 outputs response data, which is generatedbased on a result of a process by the processing unit 342, to the deviceagent apparatus 13.

The above described functions of the remote management system 10 areembodied by hardware (see FIG. 2) included in the remote devicemanagement apparatus 11, the remote management agent apparatus 12, thedevice agent apparatus 13, and the management target device 14.Specifically, the communication mode definition information storage unit310, the mapping information storage unit 320, and the management targetdevice information storage unit 330 are embodied by a storage unit 204.Other functions are embodied by a CPU 201 executing program(s) stored ina ROM 202 or a storage unit 204.

The program(s) may be provided to a user in a state installed in theremote device management apparatus 11, the remote management agentapparatus 12, the device agent apparatus 13, or the management targetdevice 14. Alternatively, the program(s) may be supplied from outsidethe remote management system 10, and be installed into the remote devicemanagement apparatus 11, the remote management agent apparatus 12, thedevice agent apparatus 13, or the management target device 14. In thelatter case, the program(s) may be provided by distributing an externalstorage device (such as a USB memory, a memory card, or a CD-ROM) inwhich the program(s) is/are installed. Alternatively, the program(s) maybe provided by storing in a server on a network (such as the Internet)in a downloadable state.

<Flow of Remote Management Process in Remote Management System 10>

FIG. 4 is a sequence diagram illustrating a flow of a remote managementprocess performed in the remote management system 10 according to thefirst embodiment of the present disclosure. The process illustrated inFIG. 4 is started, for example, when a device administrator inputs, to aremote device management apparatus 11, an instruction targeted to amanagement target device 14. Alternatively for example, the process maybe started periodically based on the service definition informationmaintained by the remote device management apparatus 11.

Note that FIG. 4 describes an example in which a remote devicemanagement apparatus 11 a obtains information from a management targetdevice 14 a by sending an information acquisition request (an example ofrequest data) to the management target device 14 a.

Also in this example, suppose a case that the following information isstored in the communication mode definition information storage unit 310and the mapping information storage unit 320. In the communication modedefinition information stored in the communication mode definitioninformation storage unit 310, “SNMP” is recorded as a communication modesupported by the management target device 14 a. Further, in the firstmapping information stored in the mapping information storage unit 320,“device agent apparatus 13 a” is recorded as a device agent apparatus 13associated with the management target device 14 a. Further, in thesecond mapping information stored in the mapping information storageunit 320, “remote device management apparatus 11 a” is recorded as aremote device management apparatus 11 associated with the device agentapparatus 13 a.

First, the request data transmitter 311 in the remote device managementapparatus 11 a sends, to the remote management agent apparatus 12, aninformation acquisition request targeted to the management target device14 a (step S401).

When the request data receiver 321 in the remote management agentapparatus 12 receives the information acquisition request, the deviceagent apparatus identifying unit 322 identifies a device agent apparatus13 associated with the management target device 14 a, based on the firstmapping information stored in the mapping information storage unit 320(step S402). In the example illustrated in FIG. 4, “device agentapparatus 13 a” is identified as a device agent apparatus 13 associatedwith the management target device 14 a.

Next, the request data forwarder 323 forwards the informationacquisition request to the device agent apparatus 13 a (step S403).

In the device agent apparatus 13 a, when the communication unit toremote management agent apparatus 331 receives the informationacquisition request, the communication mode identifying unit 332identifies the management target device 14 a as an informationacquisition target, based on identification information designated bythe information acquisition request (step S404). The communication modeidentifying unit 332 further identifies a communication mode and acommunication setting used for communication with the management targetdevice 14 a, based on the identification information of the managementtarget device 14 a, the communication mode definition information, andthe management target device information (step S405).

In the example illustrated in FIG. 4, “SNMP” is identified as thecommunication mode used for the communication with the management targetdevice 14 a. Next, by performing communication in compliance with thecommunication mode (SNMP) and the communication setting identified atstep S404, the communication unit to management target device 333 sendsthe information acquisition request to the management target device 14 a(step S406).

When the request receiver 341 receives the information acquisitionrequest in the management target device 14 a, the processing unit 342performs a process for extracting information according to theinformation acquisition request, and the response output unit 343outputs, as response data, the extracted information to the device agentapparatus 13 a (step S407).

In the device agent apparatus 13 a, when the communication unit tomanagement target device 333 receives the response data output by themanagement target device 14 a, the communication unit to remotemanagement agent apparatus 331 sends the response data to the remotemanagement agent apparatus 12 (step S408).

When the remote management agent apparatus 12 receives the response datasent from the device agent apparatus 13 a, the remote management agentapparatus 12 identifies, based on identification information of thedevice agent apparatus 13 a designated by the response data, and basedon the second mapping information stored in the mapping informationstorage unit 320, the remote device management apparatus 11 a as adestination where the response data is to be forwarded (step S409).

Next, the response data forwarder 325 forwards the response data to theremote device management apparatus 11 a (step S410). When the responsedata receiver 312 receives the response data in the remote devicemanagement apparatus 11 a, the remote management system 10 terminatesthe series of the processes illustrated in FIG. 4.

<Flow of Device Agent Apparatus Setting Process Performed in RemoteManagement System 10>

FIG. 5 is a sequence diagram illustrating a flow of a device agentapparatus setting process performed in the remote management system 10according to the first embodiment of the present disclosure. In thefollowing, a case is described in which the remote device managementapparatus 11 a is associated with the device agent apparatus 13 a, andthe association (mapping) is registered with the second mappinginformation in the mapping information storage unit 320 of the remotemanagement agent apparatus 12.

First, a device administrator 17 inputs an instruction for issuing aregistration number to the remote device management apparatus 11 a (stepS501). In response to the input, the remote device management apparatus11 a sends a request for issuing a registration number to the remotemanagement agent apparatus 12 (step S502).

When the remote management agent apparatus 12 receives the request forissuing a registration number, the remote management agent apparatus 12issues a registration number (step S503). In the example described here,suppose a case in which “112233” was issued as the registration numberat step S503. After step S503, the remote management agent apparatus 12associates the remote device management apparatus 11 a with the issuedregistration number “112233” (step S504).

Next, the remote management agent apparatus 12 sends (notification of)the issued registration number “112233” to the remote device managementapparatus 11 a (step S505). Further, the remote device managementapparatus 11 a sends (notification of) the issued registration number“112233” to the device administrator 17 (step S506).

Next, the device administrator 17 inputs the registration number“112233” to the device agent apparatus 13 a (step S511). In response tothe input, the device agent apparatus 13 a sends (notification of) theinput registration number “112233” and an identifier of the device agentapparatus 13 a to the remote management agent apparatus 12 (step S512).

In response to receiving the notification, the remote management agentapparatus 12 associates an identifier of the remote device managementapparatus 11 a that is associated with the notified registration number“112233”, with the notified identifier of the device agent apparatus 13a, and stores information about the association into the second mappinginformation in the mapping information storage unit 320 of the remotemanagement agent apparatus 12 (step S513).

Next, the remote management agent apparatus 12 sends a notificationindicating a completion of a second mapping information registration tothe device agent apparatus 13 a (step S514). The device agent apparatus13 a sends (notification of) a result of the second mapping informationregistration, to the remote device management apparatus 11 a (stepS515).

<Flow of Management Target Device Adding Process in Remote ManagementSystem 10>

FIG. 6 is a sequence diagram illustrating a flow of a management targetdevice adding process performed in the remote management system 10according to the first embodiment of the present disclosure. Thefollowing describes a case in which, in response to a new addition of amanagement target device 14 a to the remote management system 10,communication mode definition information and management target deviceinformation concerning the management target device 14 a are added tothe device agent apparatus 13 a.

First, the remote device management apparatus 11 a sends, to the remotemanagement agent apparatus 12, a request for setting communication modedefinition information concerning the management target device 14 a(step S601). When the remote management agent apparatus 12 receives therequest for setting the communication mode definition informationconcerning the management target device 14 a, the remote managementagent apparatus 12 forwards the request to the device agent apparatus 13a (step S602).

When the device agent apparatus 13 a receives the request for settingthe communication mode definition information concerning the managementtarget device 14 a, the communication mode definition informationsetting unit 335 sets the communication mode definition informationconcerning the management target device 14 a to the device agentapparatus 13 a (step S603).

Next, the remote device management apparatus 11 a sends, to the remotemanagement agent apparatus 12, a request for adding management targetdevice information concerning the management target device 14 a (stepS611). When the remote management agent apparatus 12 receives therequest for adding the management target device information concerningthe management target device 14 a, the remote management agent apparatus12 forwards the request to the device agent apparatus 13 a (step S612).

When the device agent apparatus 13 a receives the request for adding themanagement target device information concerning the management targetdevice 14 a, the management target device information registration unit334 additionally registers the management target device informationconcerning the management target device 14 a with the management targetdevice information storage unit 330 (step S613). Next, the device agentapparatus 13 a sends a notification indicating a registration completionof the management target device information to the remote managementagent apparatus 12 (step S614). When the remote management agentapparatus 12 receives the notification, the mapping informationregistration unit 326 adds the association (mapping) of the managementtarget device 14 a with the device agent apparatus 13 a to the firstmapping information stored in the mapping information storage unit 320(step S615).

<Example of First Mapping Information>

FIG. 7 is a diagram illustrating an example of the first mappinginformation stored in the mapping information storage unit 320 of theremote management system 10 according to the first embodiment of thepresent disclosure. As illustrated in FIG. 7, a mapping between amanagement target device 14 and a device agent apparatus 13 (a deviceagent apparatus 13 capable of communicating in compliance with acommunication mode supported by the management target device 14) isrecorded in the first mapping information.

The first mapping information is stored in the mapping informationstorage unit 320 of the remote management agent apparatus 12. The firstmapping information is referenced when the device agent apparatusidentifying unit 322 in the remote management agent apparatus 12identifies a device agent apparatus 13 used for communicating with amanagement target device 14. For example, if an identifier of amanagement target device 14, included in request data as a destinationof the request data, is “Device333333”, the device agent apparatusidentifying unit 322 identifies a device agent apparatus 13 having anidentifier “Gateway12345” as a device agent apparatus 13 used forcommunicating with the management target device 14, based on the firstmapping information illustrated in FIG. 7.

<Example of Second Mapping Information>

FIG. 8 is a diagram illustrating an example of the second mappinginformation stored in the mapping information storage unit 320 of theremote management system 10 according to the first embodiment of thepresent disclosure. As illustrated in FIG. 8, a mapping between a remotedevice management apparatus 11 and a device agent apparatus 13 isrecorded in the second mapping information.

The second mapping information is stored in the mapping informationstorage unit 320 of the remote management agent apparatus 12. The secondmapping information is referenced when the response data forwarder 325in the remote management agent apparatus 12 identifies a remote devicemanagement apparatus 11 to which response data received from a deviceagent apparatus 13 is to be forwarded. For example, if an identifier ofa device agent apparatus 13, included in response data as a destination,is “Gateway12345”, the response data forwarder 325 identifies a remotedevice management apparatus 11 having an identifier “Application_a” as aremote device management apparatus 11 to which the response data is tobe forwarded, based on the second mapping information illustrated inFIG. 8.

<Data Structure of Communication Mode Definition Information>

FIG. 9 is a diagram illustrating an exemplary data structure of thecommunication mode definition information stored in the communicationmode definition information storage unit 310 of the remote managementsystem 10 according to the first embodiment of the present disclosure.In the communication mode definition information, a definition of acommunication mode supported by a management target device 14 isrecorded.

In the example of the communication mode definition informationillustrated in FIG. 9, the communication mode definition informationincludes data items of “Protocol Type”, “Supported Device Type”,“Communication Port”, and “Detailed Definition of CommunicationProtocol”.

The “Protocol Type” stores information for identifying a communicationprotocol supported by a management target device 14, such as HTTP, SNMP,ICMP, or MQTT. The “Supported Device Type” stores a type of a managementtarget device 14, supporting the communication mode (protocol). The“Communication Port” stores information about communication port, suchas “80/tcp”, which is used for communication with a management targetdevice 14. The “Detailed Definition of Communication Protocol” stores adetailed definition of the communication protocol.

When a management target device 14 is newly added, the communicationmode definition information having the data structure described here isset to a device agent apparatus 13 capable of communicating with theadded management target device 14, in response to a request from aremote device management apparatus 11. By the communication modedefinition information, the device agent apparatus 13 can identify acommunication mode to be used for communicating with the managementtarget device 14.

<Data Structure of Management Target Device Information>

FIG. 10 is a diagram illustrating an exemplary data structure of themanagement target device information stored in the management targetdevice information storage unit 330 of the remote management system 10according to the first embodiment of the present disclosure. In themanagement target device information, communication setting informationconcerning a management target device 14 is stored.

In the example of the management target device information illustratedin FIG. 10, the management target device information includes data itemsof “Device Identifier”, “Device Type”, “IP Address”, and “AdditionalInformation”.

The “Device Identifier” stores identification information for uniquelyidentifying a management target device 14. An example of informationthat can be used for the identification information is a MAC address.The “Device Type” stores information representing a type of themanagement target device 14. This information is used for matching themanagement target device 14 with the communication mode definitioninformation. The “IP Address” stores an IP address of the managementtarget device 14. The “Additional Information” stores informationconcerning a monitoring interval, a network interface used forcommunication, and the like.

When a management target device 14 is newly added, the management targetdevice information having the data structure described here isadditionally registered with the management target device informationstorage unit 330 in a device agent apparatus 13 capable of communicatingwith the added management target device 14, in response to a requestfrom a remote device management apparatus 11. By the management targetdevice information, the device agent apparatus 13 can identify acommunication setting to be used for communicating with the managementtarget device 14.

<Flow of Schedule Execution Process in Remote Management System 10>

FIG. 11 is a sequence diagram illustrating a flow of a scheduleexecution process performed in the remote management system 10 accordingto the first embodiment of the present disclosure. In the following, anexample of processes for registering schedule execution information froma remote device management apparatus 11 a with a device agent apparatus13 a, for periodically acquiring information about a management targetdevice 14 a by the device agent apparatus 13 a, and for providing theacquired information to the remote device management apparatus 11 a,will be described.

First, the remote device management apparatus 11 a sends a request forregistering schedule execution information to the remote managementagent apparatus 12 (step S1101). The schedule execution information isentered to the remote device management apparatus 11 a by the deviceadministrator 17 (see FIG. 5). When the remote management agentapparatus 12 receives the request for registering the schedule executioninformation, the remote management agent apparatus 12 forwards therequest to the device agent apparatus 13 a (step S1102). When the deviceagent apparatus 13 a receives the request for registering the scheduleexecution information, the schedule information registration unit 336registers the schedule execution information with the scheduleinformation storage unit 337 (step S1103).

Thereafter, when the device agent apparatus 13 a detects an instance oftime to perform schedule execution, which is set in the scheduleexecution information (step S1104), the communication mode identifyingunit 332 identifies a management target device 14 from which informationis to be acquired (the management target device 14 a is identified inthe example described here) (step S1105). Next, the communication modeidentifying unit 332 identifies a communication mode and a communicationsetting that are used for communication with the management targetdevice 14 a, based on the identification information of the managementtarget device 14 a, the communication mode definition information, andthe management target device information (step S1106). In the exampleillustrated in FIG. 11, as the communication mode used for thecommunication with the management target device 14 a, “SNMP” isidentified.

Next, by performing communication in compliance with the communicationmode and the communication setting identified at step S1106, thecommunication unit to management target device 333 sends an informationacquisition request to the management target device 14 a (step S1107).

When the request receiver 341 receives the information acquisitionrequest in the management target device 14 a, the processing unit 342performs a process for extracting information according to theinformation acquisition request, and the response output unit 343outputs the extracted information to the device agent apparatus 13 a asresponse data (step S1108).

In the device agent apparatus 13 a, when the communication unit tomanagement target device 333 receives the response data output from themanagement target device 14 a, the communication unit to remotemanagement agent apparatus 331 sends the response data to the remotemanagement agent apparatus 12 (step S1109).

When the remote management agent apparatus 12 receives the response datasent from the device agent apparatus 13 a, the remote management agentapparatus 12 identifies the remote device management apparatus 11 a as adestination where the response data is to be forwarded, based onidentification information of the device agent apparatus 13 a designatedby the response data, and based on the second mapping information storedin the mapping information storage unit 320 (step S1110).

Next, the response data forwarder 325 forwards the response data to theremote device management apparatus 11 a (step S1111). When the responsedata receiver 312 receives the response data in the remote devicemanagement apparatus 11 a, the remote management system 10 terminatesthe series of the processes illustrated in FIG. 11.

It should be noted that the remote management system 10 executes theabove processes from steps S1104 to S1111 at every instance of time toperform schedule execution recorded in the schedule executioninformation. Therefore, the remote device management apparatus 11 a canacquire information about the management target device 14 aperiodically, without sending an information acquisition request.

As described above, in the remote management system 10 according to thefirst embodiment of the present disclosure, the remote management agentapparatus 12 identifies a device agent apparatus 13 capable ofcommunicating in compliance with a communication mode supported by amanagement target device 14, and forwards request data from a remotedevice management apparatus 11 to the identified device agent apparatus13. Accordingly, in a case in which a new electronic device is added asa management target device 14 in the remote management system 10, byonly performing a setting such that the remote management agentapparatus 12 can identify a device agent apparatus 13 communicable withthe management target device 14, the remote management system 10 will beable to manage the management target device 14 remotely. Hence,according to the remote management system 10, various electronic deviceseach supporting different types of communication modes can be easilyadded as management target devices.

Especially, the remote management system 10 identifies a device agentapparatus 13 capable of communicating with a management target device14, by referring to the first mapping information storing a mappingbetween the management target device 14 and the device agent apparatus13. Therefore, according to the remote management system 10, in a casein which a new electronic device is added as a management target device14 in the remote management system 10, by only performing a simplesetting to add the mapping between the management target device 14 andthe device agent apparatus 13 to the first mapping information, theremote management system 10 will be able to manage the management targetdevice 14 remotely.

Further in the remote management system 10, the remote management agentapparatus 12 refers to the second mapping information storing a mapping(association) between a device agent apparatus 13 and a remote devicemanagement apparatus 11, to identify a remote device managementapparatus 11 associated with a device agent apparatus 13 from whichresponse data is sent, and determines the identified remote devicemanagement apparatus 11 as a remote device management apparatus 11 towhich response data is to be forwarded. Therefore, even when multipleremote device management apparatuses 11 are present, the remotemanagement system 10 can easily and securely identify a remote devicemanagement apparatus 11 to which response data, which is output from amanagement target device 14, is to be forwarded.

Further in the remote management system 10, a device agent apparatus 13identifies a communication mode supported by a management target device14, by referring to communication mode definition information, andperforms communication with the management target device 14 incompliance with the identified communication mode. Therefore, accordingto the remote management system 10, when a new electronic device isadded as a management target device 14 in the remote management system10, by only setting a communication mode supported by the managementtarget device 14 to the communication mode definition information, adevice agent apparatus 13 can communicate with the management targetdevice 14 in compliance with the appropriate communication mode.

Further in the remote management system 10, when a management targetdevice 14 is newly added, communication mode definition informationconcerning the management target device 14 and management target deviceinformation storing communication setting information of the managementtarget device 14 are set/registered dynamically with a device agentapparatus 13. Therefore, according to the remote management system 10, adevice agent apparatus 13 can use the communication mode definitioninformation and the management target device information without settingthe communication mode definition information and the management targetdevice information to the device agent apparatus 13 by a systemadministrator manually.

In the first embodiment described above, it should be noted thatfunctions of the remote management agent apparatus 12 may be embodied bya physically single apparatus, or by multiple physical apparatuses. Forexample, some of the functions of the remote management agent apparatus12 may reside in a device outside the remote management agent apparatus12.

Similarly in the first embodiment described above, functions of thedevice agent apparatus 13 may be embodied by a physically singleapparatus, or by multiple physical apparatuses. For example, some of thefunctions of the device agent apparatus 13 may reside in a deviceoutside the device agent apparatus 13.

Second Embodiment

In the following, a second embodiment of the present disclosure will bedescribed with reference to FIG. 12. The second embodiment describes acase in which a target of application is an industrial equipmentmanagement system. FIG. 12 is a view illustrating an overallconfiguration of an industrial equipment management system 20 accordingto the second embodiment of the present disclosure. The industrialequipment management system 20 is an example of a “remote managementsystem” described in the claims.

As illustrated in FIG. 12, the industrial equipment management system 20according to the second embodiment includes customer systems 60 a, 60 b,and 60 c, and a management system 70. The customer systems 60 a, 60 b,and 60 c, and the management system 70 are all connected to the Internet15. Especially, each of the customer systems 60 a, 60 b, and 60 c isconnected to the Internet 15 via a firewall 16 provided in each of thecustomer systems 60 a, 60 b, and 60 c.

The customer system 60 a is installed in a site of a customer. Thecustomer system 60 a includes a management agent apparatus 13′, amanagement target system 30, and a firewall 16. The management targetsystem 30 is a target of remote management by the management system 70.

FIG. 12 illustrates a case in which the management target system 30includes industrial equipment 31 a and a sensor 31 b. The industrialequipment 31 a and the sensor 31 b are examples of a “management targetdevice” in the claims, and have functions similar to the functions inthe management target device 14 described in the first embodiment.Examples of the industrial equipment 31 a include a processing machine,a conveyer, and an inspection machine. Examples of the sensor 31 binclude an image capturing device and a sound collecting device.

The management agent apparatus 13′ is an example of a “device agentapparatus” in the claims, and have functions similar to the functions inthe device agent apparatus 13 described in the first embodiment. Themanagement agent apparatus 13′ is connected to the management targetsystem 30 and the firewall 16 via a LAN (Local Area Network). Themanagement agent apparatus 13′ includes a firmware update function toupdate firmware, installed in the industrial equipment 31 a or thesensor 31 b, using an Internet connection.

The customer system 60 b is installed in another customer's site. Thecustomer system 60 b includes a device with agent 33 and a firewall 16.The device with agent 33 is a target of remote management by themanagement system 70. The device with agent 33 is an example of a“management target device” and a “device agent apparatus” in the claims,and have functions similar to the functions in the management targetdevice 14 and the device agent apparatus 13 described in the firstembodiment.

Examples of the device with agent 33 include industrial equipment (suchas a processing machine, a conveyer, and an inspection machine), and asensor (such as an image capturing device and a sound collectingdevice). The device with agent 33 is connected to the firewall 16 via aLAN. The device with agent 33 includes a firmware update function toupdate firmware, installed in the device with agent 33, using anInternet connection.

The customer system 60 c is installed in yet another customer's site.The customer system 60 c includes a management agent apparatus 13′,multiple management target systems 30, and a firewall 16. Each of themanagement target systems 30 is a target of remote management by themanagement system 70.

FIG. 12 illustrates a case in which at least one of the managementtarget systems 30 includes industrial equipment 31 a, a sensor 31 b, anda management agent apparatus 32. The industrial equipment 31 a and thesensor 31 b are examples of a “management target device” in the claims,and have functions similar to the functions in the management targetdevice 14 described in the first embodiment. Examples of the industrialequipment 31 a include a processing machine, a conveyer, and aninspection machine. Examples of the sensor 31 b include an imagecapturing device and a sound collecting device.

The management agent apparatuses 13′ and 32 are examples of a “deviceagent apparatus” in the claims, and have functions similar to thefunctions in the device agent apparatus 13 described in the firstembodiment. The management agent apparatuses 13′ and 32 are connected tothe management target systems 30 and the firewall 16 via a LAN. Themanagement agent apparatuses 13′ and 32 include a firmware updatefunction to update firmware, installed in the industrial equipment 31 aor the sensor 31 b, using an Internet connection.

In the customer system 60 c, to alleviate workload increase of themanagement agent apparatus 13′, the management agent apparatus 32 isadditionally provided. An update of firmware of the industrial equipment31 a or the sensor 31 b in the management target system 30 is performedby the management agent apparatus 32. The management agent apparatus 13′performs a function to centrally perform remote management of multiplemanagement target systems 30 using an Internet connection with themanagement system 70.

The management system 70 is a system for remotely managing variousmanagement target devices (the industrial equipment 31 a, the sensor 31b, and the device with agent 33) in each of the customer systems 60 a,60 b, and 60 c via the Internet 15. FIG. 12 illustrates a case in whichthe management system 70 includes a remote device management apparatus11′ and a remote management agent apparatus 12′.

The remote device management apparatus 11′ includes functions similar tothe functions of the remote device management apparatus 11 described inthe first embodiment. The remote management agent apparatus 12′ includesfunctions similar to the functions of the remote management agentapparatus 12 described in the first embodiment. For example, themanagement system 70 issues various operating instructions (such aschanging setting value, updating a firmware, or turning on/off power) tothe management target devices in each of the customer systems 60 a, 60b, and 60 c, or acquires various information (such as statusinformation, setting information, or log information) from themanagement target devices in each of the customer systems 60 a, 60 b,and 60 c.

In the above industrial equipment management system 20, the remotedevice management apparatus 11′, the remote management agent apparatus12′, the management agent apparatus 13′, the management agent apparatus32, and the device with agent 33 include general purpose computercomponents. That is, similar to the hardware configuration illustratedin FIG. 2, these apparatuses include at least a CPU for executingvarious programs, a ROM, a RAM, and a storage unit used by the CPUexecuting the programs, and a communication unit such as a modem or anetwork interface.

In the industrial equipment management system 20 configured as describedabove, similar to the remote management system 10 according to the firstembodiment, the remote management agent apparatus 12′ in the managementsystem 70 identifies a device agent apparatus (a management agentapparatus 13′, a management agent apparatus 32, or a device with agent33) capable of communicating in compliance with a communication modesupported by a management target device (an industrial equipment 31 a, asensor 31 b, or a device with agent 33), and forwards request data fromthe remote device management apparatus 11′ in the management system 70to the identified device agent apparatus.

Accordingly, in a case in which a new electronic device is added as amanagement target device in the industrial equipment management system20, by only performing a setting such that a remote management agentapparatus 12′ can identify a device agent apparatus communicable withthe management target device, the industrial equipment management system20 will be able to manage the management target device remotely. Hence,according to the industrial equipment management system 20, variouselectronic devices each supporting different types of communicationmodes can be easily added as management target devices.

A management target device, which is treated as a target of remotemanagement by the remote management system in the present disclosure, isnot limited to an imaging device, and may be various types of equipmenthaving a communication function (such as a network-connected homeappliance, a vending machine, medical equipment, industrial equipment,power supply equipment, an air conditioning system, or a measuringsystem for gas, water, electricity, and the like). In addition, amanagement target device may be a detection device (such as an imagecapturing device and a sound collecting device) which is provided aroundthe above equipment to detect a state of the equipment.

Examples of industrial equipment include processing equipment,inspection equipment, conveying equipment, and picking equipment. In acase in which industrial equipment is to be treated as a managementtarget device, the industrial equipment may send, as response data,identification information of the equipment, operating status of theequipment, presence or absence of an abnormal operation of theequipment, information about replacement time of consumables, a resultof inspection by the equipment, or the like, to the management system70. In sending the response data, various types of transmitting methodsmay be used. For example, the response data to be sent may be formattedas an image format.

Examples of medical equipment include an ophthalmoscopy device, an X-rayinspection apparatus, a sphygmomanometer, a body fat meter, anoptometer, and a pacemaker. In a case in which medical equipment is tobe treated as a management target device, the medical equipment maysend, as response data, identification information of the equipment,operating status of the equipment, presence or absence of an abnormaloperation of the equipment, a result of measurement by the equipment, orthe like, to the management system 70. In sending the response data,various types of transmitting methods may be used. For example, theresponse data to be sent may be formatted as an image format.

Although the preferred embodiments of the present invention have beendescribed, the present invention is not limited to these embodiments.Various variations and enhancements may be applied within the scope ofthe subject matters described in the claims.

What is claimed is:
 1. A remote management agent apparatus for a remotemanagement system, the remote management system including a remotedevice management apparatus, a management target device managed by theremote device management apparatus remotely, the remote management agentapparatus, and a plurality of device agent apparatuses configured totransmit data received from the remote management agent apparatus to themanagement target device, the remote management agent apparatuscomprising a memory storing a program and a processor configured toexecute the program to implement a process including: receiving requestdata issued from the remote device management apparatus to themanagement target device; identifying, from among the plurality ofdevice agent apparatuses, a device agent apparatus capable ofcommunicating in compliance with a communication mode supported by themanagement target device; and in response to the identifying, forwardingthe request data to the identified device agent apparatus to cause theidentified device agent apparatus to transmit the request data to themanagement target device.
 2. The remote management agent apparatusaccording to claim 1, the process further including: referring to firstmapping information representing a mapping between the management targetdevice and the device agent apparatus, in order to identify the deviceagent apparatus capable of communicating in compliance with thecommunication mode supported by the management target device.
 3. Theremote management agent apparatus according to claim 1, the processfurther including: receiving, via the device agent apparatus, responsedata output by the management target device in response to the requestdata; identifying, by referring to second mapping informationrepresenting a mapping between the device agent apparatus and the remotedevice management apparatus, the remote device management apparatusassociated with the device agent apparatus via which the response datais sent; determining the identified remote device management apparatusas a destination of the response data; and forwarding the response datato the remote device management apparatus.
 4. A remote management systemcomprising: a remote device management apparatus; a management targetdevice managed by the remote device management apparatus remotely; aremote management agent apparatus; and a plurality of device agentapparatuses configured to transmit data received from the remotemanagement agent apparatus to the management target device; wherein theremote management agent apparatus includes a memory storing a programand a processor configured to execute the program to implement a processincluding: receiving request data issued from the remote devicemanagement apparatus to the management target device; identifying, fromamong the plurality of device agent apparatuses, a device agentapparatus capable of communicating in compliance with a communicationmode supported by the management target device; and in response to theidentifying, forwarding the request data to the identified device agentapparatus to cause the identified device agent apparatus to transmit therequest data to the management target device.
 5. The remote managementsystem according to claim 4, the device agent apparatus being configuredto identify a communication mode supported by the management targetdevice by referring to communication mode definition informationincluding a definition of the communication mode supported by themanagement target device, and to communicate with the management targetdevice in compliance with the identified communication mode supported bythe management target device.
 6. The remote management system accordingto claim 5, the device agent apparatus being configured: in response toan addition of a new management target device, to register thecommunication mode definition information and communication settinginformation for the new management target device with the device agentapparatus; and to communicate with the new management target device incompliance with the communication mode supported by the new managementtarget device, based on the registered communication mode definitioninformation, and on the registered communication setting information. 7.The remote management system according to claim 5, the device agentapparatus being further configured to acquire, by a communication withthe management target device, information concerning the managementtarget device at every instance of time to perform schedule executionrecorded in the schedule execution information, to provide theinformation concerning the management target device to the remote devicemanagement apparatus.
 8. The remote management system according to claim4, the process further including: referring to first mapping informationrepresenting a mapping between the management target device and thedevice agent apparatus, in order to identify the device agent apparatuscapable of communicating in compliance with the communication modesupported by the management target device.
 9. The remote managementsystem according to claim 4, the process further including: receiving,via the device agent apparatus, response data output by the managementtarget device in response to the request data; identifying, by referringto second mapping information representing a mapping between the deviceagent apparatus and the remote device management apparatus, the remotedevice management apparatus associated with the device agent apparatusvia which the response data is sent; determining the identified remotedevice management apparatus as a destination of the response data; andforwarding the response data to the remote device management apparatus.10. A remote management method for a remote management system includinga remote device management apparatus, a management target device managedby the remote device management apparatus remotely, a remote managementagent apparatus, and a plurality of device agent apparatuses configuredto transmit data received from the remote management agent apparatus tothe management target device, the method being performed by the remotemanagement agent apparatus comprising: receiving request data issuedfrom the remote device management apparatus to the management targetdevice; identifying, from among the plurality of device agentapparatuses, a device agent apparatus capable of communicating incompliance with a communication mode supported by the management targetdevice; and in response to the identifying, forwarding the request datato the identified device agent apparatus to cause the identified deviceagent apparatus to transmit the request data to the management targetdevice.
 11. The remote management method according to claim 10, furthercomprising: referring to first mapping information representing amapping between the management target device and the device agentapparatus, in order to identify the device agent apparatus capable ofcommunicating in compliance with the communication mode supported by themanagement target device.
 12. The remote management method according toclaim 10, further comprising: receiving, via the device agent apparatus,response data output by the management target device in response to therequest data; identifying, by referring to second mapping informationrepresenting a mapping between the device agent apparatus and the remotedevice management apparatus, the remote device management apparatusassociated with the device agent apparatus via which the response datais sent; determining the identified remote device management apparatusas a destination of the response data; and forwarding the response datato the remote device management apparatus.
 13. The remote managementmethod according to claim 10, further comprising: registering with thedevice agent apparatus, in response to an addition of a new managementtarget device, communication mode definition information including adefinition of the communication mode supported by the new managementtarget device; and performing communication between the device agentapparatus and the new management target device in compliance with thecommunication mode supported by the new management target device, basedon the communication mode definition information.
 14. The remotemanagement method according to claim 13, further comprising: acquiring,through the device agent apparatus, information concerning themanagement target device from the management target device at everyinstance of time to perform schedule execution recorded in the deviceagent apparatus, to provide the information concerning the managementtarget device to the remote device management apparatus.